MediaWiki MCP adapter

Created By
lucamauria year ago
A custom Model Context Protocol (MCP) adapter for interacting with MediaWiki and WikiBase APIs. This adapter allows you to fetch and edit MediaWiki pages programmatically using the MCP framework.
Overview

What is MediaWiki MCP Adapter?

MediaWiki MCP Adapter is a custom Model Context Protocol (MCP) adapter designed for interacting with MediaWiki and WikiBase APIs, allowing users to programmatically fetch and edit MediaWiki pages.

How to use MediaWiki MCP Adapter?

To use the MediaWiki MCP Adapter, clone the repository, install the dependencies, configure the adapter with your MediaWiki and WikiBase API endpoints, and start the MCP server.

Key features of MediaWiki MCP Adapter?

  • Fetch the content of a MediaWiki page.
  • Edit a MediaWiki page with new content and an optional summary.
  • Configurable API base URLs for different MediaWiki and WikiBase instances.

Use cases of MediaWiki MCP Adapter?

  1. Automating the retrieval of content from MediaWiki pages.
  2. Programmatically updating MediaWiki pages with new information.
  3. Integrating MediaWiki content into other applications or services.

FAQ from MediaWiki MCP Adapter?

  • What are the requirements to use the MediaWiki MCP Adapter?

You need Node.js (v16 or later) and a MediaWiki instance with API access enabled.

  • Can I configure the adapter for different MediaWiki instances?

Yes! You can set custom API base URLs for different MediaWiki and WikiBase instances.

  • Is there any testing implemented in the project?

Currently, no tests are implemented, but you can add tests in the test directory.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
lucamauri
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

3 hours ago
Myrsu
@VidhiJav

2 days ago
Tavily Mcp
@tavily-ai

JavaScript
a year ago